1 00:00:08,660 --> 00:00:09,350 Great. 2 00:00:10,310 --> 00:00:20,360 So today we will continue in second topic in the advance batch, so please, if you have questions on 3 00:00:20,360 --> 00:00:25,160 previous sessions, if you have any doubts, let us know. 4 00:00:25,160 --> 00:00:30,980 Then we will clear before starting this session anyone has a question. 5 00:00:35,530 --> 00:00:36,580 And any time. 6 00:00:37,900 --> 00:00:38,470 And. 7 00:00:45,170 --> 00:00:46,140 OK, no questions. 8 00:00:46,230 --> 00:00:47,300 Let's start today 9 00:00:49,820 --> 00:00:52,310 Karani, let's start today's session, please. 10 00:00:54,400 --> 00:00:55,180 OK, thank you. 11 00:00:56,650 --> 00:01:05,530 So I am outside today, so you may hear some background, some some some background, some some noise 12 00:01:05,530 --> 00:01:06,190 from the background. 13 00:01:06,190 --> 00:01:09,550 So just ignore that because I'm outside. 14 00:01:09,550 --> 00:01:10,650 I'm not in the house today. 15 00:01:11,020 --> 00:01:13,120 So let me share my screen. 16 00:01:15,170 --> 00:01:16,940 I am over, I'm old enough. 17 00:01:19,320 --> 00:01:21,000 Yes, you are edible. 18 00:01:21,810 --> 00:01:23,020 Everything is OK. 19 00:01:23,700 --> 00:01:24,480 Great, great. 20 00:01:24,510 --> 00:01:25,770 So let's let's move on. 21 00:01:26,190 --> 00:01:28,710 So today I want us to look at this. 22 00:01:28,920 --> 00:01:31,050 OK, so someone was money. 23 00:01:31,160 --> 00:01:35,490 You mentioned that there are this some team that wanted to know how to use GitHub. 24 00:01:38,100 --> 00:01:38,650 GitHub. 25 00:01:39,120 --> 00:01:41,060 This is no number 18. 26 00:01:41,610 --> 00:01:50,610 So I wanted to know I wanted to know exactly how use case because because GitHub ideally you can you 27 00:01:50,610 --> 00:01:52,890 can manage GitHub in two is in your opinion. 28 00:01:53,700 --> 00:01:59,580 There is one where you you may be needing to manage the whole software that you are creating that is 29 00:01:59,580 --> 00:02:04,980 including your next the other one, which ideally doesn't make a lot of sense. 30 00:02:05,910 --> 00:02:12,960 Number two is you manage the apps that you are creating and you let your next manager they have created. 31 00:02:14,650 --> 00:02:15,120 OK. 32 00:02:15,790 --> 00:02:27,510 Actually, it makes sense to make to to to speed up this topic since Muhammad Ali Aboubacar from and 33 00:02:27,510 --> 00:02:36,760 his team here in Tunisia, they need to work to cooperate or to start working as a team in the same 34 00:02:36,760 --> 00:02:39,480 for the same application. 35 00:02:40,380 --> 00:02:43,030 You can add more details. 36 00:02:43,050 --> 00:02:45,030 Muhammad Ali, Boubacar 37 00:02:48,900 --> 00:02:49,670 aboutus. 38 00:02:49,680 --> 00:02:52,730 You're OK. 39 00:02:53,070 --> 00:02:58,330 We will start developing our our solution using therapy. 40 00:02:58,450 --> 00:03:07,790 Next, we will want to know how can we work together to get a. 41 00:03:10,060 --> 00:03:12,850 As a team, you see Karani. 42 00:03:14,040 --> 00:03:22,260 Yeah, so so together, you mean OK, what I can show you here is, yes, Google. 43 00:03:23,670 --> 00:03:24,930 When we will 44 00:03:27,940 --> 00:03:39,420 will, uh, developing the application, we will create a customized DOCTYPE or customized existing 45 00:03:39,420 --> 00:03:39,940 today. 46 00:03:40,320 --> 00:03:45,560 So we we shall be working in the same database. 47 00:03:49,210 --> 00:03:54,100 So how can we I mean, as many as this? 48 00:04:01,010 --> 00:04:10,310 OK, so now, now, so they have used GitHub before because what I would like to understand is whether 49 00:04:10,310 --> 00:04:16,480 we are talking about GitHub or the problem here is using Europeanist with GitHub. 50 00:04:17,870 --> 00:04:20,060 Is it how you use GitHub before as a team? 51 00:04:20,900 --> 00:04:21,650 Of course. 52 00:04:21,650 --> 00:04:22,100 Of course. 53 00:04:23,300 --> 00:04:34,850 OK, so what you are going to do me open let me open GitHub here is important one number one ERP next 54 00:04:35,480 --> 00:04:37,010 you are going to manage GitHub 55 00:04:40,070 --> 00:04:43,580 font pseudo soon. 56 00:04:44,680 --> 00:04:44,990 Very 57 00:04:48,080 --> 00:04:48,640 soon. 58 00:04:51,850 --> 00:04:52,540 He hasn't 59 00:04:55,900 --> 00:04:57,730 been able to. 60 00:04:59,080 --> 00:05:09,280 So what happens here is you are not you are not going to be managing managing all these things inside 61 00:05:09,280 --> 00:05:09,980 of your app. 62 00:05:10,480 --> 00:05:15,900 What you need to do to start with is your need to manage to manage the apparatus have created. 63 00:05:16,420 --> 00:05:23,830 So if here we come to our library management app and released, let me list everything here already 64 00:05:23,950 --> 00:05:25,130 it is initialized. 65 00:05:25,240 --> 00:05:32,920 So if you try to get in it from this file, this directory of it will tell you that it has only been 66 00:05:32,930 --> 00:05:33,510 initialized. 67 00:05:34,090 --> 00:05:39,400 So what you need to do is to create after you have created, you are on GitHub. 68 00:05:40,450 --> 00:05:47,230 Then next thing you need to do is to just connect, connect you up with your people and then you can 69 00:05:47,230 --> 00:05:47,800 share. 70 00:05:49,020 --> 00:05:53,230 And you can say you can share your report with the US team. 71 00:05:53,740 --> 00:05:57,560 Now, you have mentioned you have mentioned about duct tape. 72 00:05:57,840 --> 00:06:04,990 And one thing that's very important to this, Mohammed, is that us, Karen? 73 00:06:07,700 --> 00:06:08,180 Karani. 74 00:06:10,090 --> 00:06:10,950 Yeah, I'm listening. 75 00:06:11,300 --> 00:06:20,210 Yeah, actually, the request we got it from Mohammed and his team, but overall, we will deliver your 76 00:06:20,230 --> 00:06:22,840 Phoenix instance and custom apps with GitHub. 77 00:06:23,230 --> 00:06:29,050 The point, managing your Phoenix with GitHub as an answer to their request. 78 00:06:29,050 --> 00:06:32,890 And we deliver the point for all for all of us. 79 00:06:32,890 --> 00:06:39,580 We are keen to understand GitHub mechanism, how we will use this. 80 00:06:39,580 --> 00:06:46,840 It is not only to reply these questions, but we will deliver the topics as a topics. 81 00:06:46,870 --> 00:06:47,740 You've got what I mean. 82 00:06:50,780 --> 00:06:52,630 Yeah, yeah, that's it. 83 00:06:53,470 --> 00:06:55,340 Sorry to interrupt and continue. 84 00:06:56,890 --> 00:07:06,400 OK, so let's go to GitHub, GitHub and create a report so I will create a new repository here. 85 00:07:07,420 --> 00:07:16,680 I will call it ERP training and I'll go ahead and public know. 86 00:07:16,720 --> 00:07:24,370 Let me make this a private and I will save it when you save, when you save that. 87 00:07:24,370 --> 00:07:26,640 And there's an echo I don't know from where. 88 00:07:27,100 --> 00:07:32,200 So when you save that, you'll notice that this will give you these commands that you should you should 89 00:07:32,200 --> 00:07:38,680 run so that you can have your food on it, so I can even go ahead and copy this. 90 00:07:38,680 --> 00:07:41,380 There's no harm of trying to initialize this a second time. 91 00:07:41,830 --> 00:07:48,570 So remember, we're in our library management instance, so I will put is so Arrhenius. 92 00:07:48,700 --> 00:07:53,050 So this one as reinitialize our GitHub repository so you can do that. 93 00:07:53,740 --> 00:07:56,410 The second thing you don't need to read me. 94 00:07:56,410 --> 00:07:58,840 If you need to order MFL, you can go ahead and do that. 95 00:07:59,230 --> 00:08:01,720 So I'll go ahead and the copy. 96 00:08:03,330 --> 00:08:11,670 The first commit, so commit, put my, my, my code online, so I'll paste this here and I will go 97 00:08:11,670 --> 00:08:12,480 ahead and push. 98 00:08:13,530 --> 00:08:15,450 So this thing is complaining. 99 00:08:15,450 --> 00:08:16,920 Let me hide this. 100 00:08:18,250 --> 00:08:24,070 Not to be a number of things that have been that have been changed here, we can see that the first 101 00:08:24,070 --> 00:08:26,060 one, the first one is there. 102 00:08:26,260 --> 00:08:27,380 Who's not why? 103 00:08:27,400 --> 00:08:33,340 We have the this are a fire and we also have untracked files here. 104 00:08:34,660 --> 00:08:41,170 So the first thing that we are going to do is to add these things to our to our GitHub local GitHub 105 00:08:41,170 --> 00:08:43,340 repo before we put we committed them online. 106 00:08:43,690 --> 00:08:44,890 So let me create this. 107 00:08:45,160 --> 00:08:49,090 And I do get and so we can just go ahead and add everything. 108 00:08:50,020 --> 00:08:54,700 But if if maybe for some reason you do not you do not want to add everything, you are not going to 109 00:08:54,700 --> 00:08:55,200 do this. 110 00:08:55,510 --> 00:09:01,990 So if I look at now, get us everything here, looks looks green. 111 00:09:01,990 --> 00:09:08,920 And that means everything has been has been added and I can go ahead and run my my get permits, get 112 00:09:08,930 --> 00:09:09,460 permit. 113 00:09:09,460 --> 00:09:11,230 And this one has been pushed online. 114 00:09:11,560 --> 00:09:13,330 So everything has gone. 115 00:09:13,720 --> 00:09:21,520 So I can now not online but on my local local GitHub repo so I can now go ahead and copy the next command. 116 00:09:23,010 --> 00:09:29,280 Which is creating this this branch so I can fix this one here go this one has been done. 117 00:09:30,650 --> 00:09:38,450 Then the next thing is no, this is adding a remote online and this is pointing to the report that we 118 00:09:38,450 --> 00:09:39,290 just created. 119 00:09:39,800 --> 00:09:45,630 So I will copy the next command and put it here and go. 120 00:09:46,070 --> 00:09:47,590 That has been done successfully. 121 00:09:47,930 --> 00:09:54,990 And now the final step is to push our code online to our to our report that is online. 122 00:09:55,010 --> 00:09:56,430 So let's go ahead and do that. 123 00:09:56,450 --> 00:09:59,030 Also listed there and go. 124 00:09:59,030 --> 00:10:00,280 And now this one is pushing. 125 00:10:00,290 --> 00:10:06,830 So this is going to ask me for my user because I do not need to set it up there so I can go ahead and 126 00:10:06,830 --> 00:10:07,760 provide that. 127 00:10:07,760 --> 00:10:14,510 Mine is currently Dekay and I'm going to give my email, my password like that. 128 00:10:15,170 --> 00:10:17,790 And that is pushing that is not pushing my code online. 129 00:10:18,410 --> 00:10:19,330 So that is done. 130 00:10:19,700 --> 00:10:26,240 So if I come to my report online and I reload, I am going to have the code. 131 00:10:26,420 --> 00:10:31,070 It is the code for my visitor code for my for my library management. 132 00:10:31,070 --> 00:10:33,260 Up to every code that we have written. 133 00:10:33,260 --> 00:10:35,960 We have utils, we have everything managed here. 134 00:10:36,290 --> 00:10:38,150 We have our python files. 135 00:10:38,810 --> 00:10:40,120 So everything is here now. 136 00:10:40,700 --> 00:10:45,640 Now, remember, this is our this is our library management app we are tracking. 137 00:10:46,160 --> 00:10:50,180 And the point I was going to take to to tell the team is that. 138 00:10:51,200 --> 00:10:57,800 When you edit, I don't remember editing tapes from the mistakes that most of the people do in the beginning, 139 00:10:57,810 --> 00:11:00,040 this is you come to your doctor. 140 00:11:00,080 --> 00:11:06,680 For instance, this one give an example, and then you come here and start customizing things from here. 141 00:11:07,520 --> 00:11:08,570 If you do this. 142 00:11:08,580 --> 00:11:11,300 Yes, this is going to create a python. 143 00:11:11,600 --> 00:11:13,040 I mean, not just one player. 144 00:11:13,670 --> 00:11:19,280 And you can push this you can push this JSON file online to track it on GitHub. 145 00:11:19,790 --> 00:11:25,520 But the most the best way to do this, this customizations, is to go to the customize. 146 00:11:26,780 --> 00:11:27,740 Customize. 147 00:11:29,920 --> 00:11:34,810 Customized, not that customized customized form. 148 00:11:35,260 --> 00:11:39,670 This is where you are going to be needing to customize all the forms that you need to customize. 149 00:11:40,120 --> 00:11:45,980 So when you customize your forms from here, what is going to happen is that the fans are going to be 150 00:11:46,000 --> 00:11:46,700 written here. 151 00:11:46,720 --> 00:11:52,300 Now, this is to directly answer the question that Mohammed asked the team. 152 00:11:53,080 --> 00:11:59,410 What the rest of the team would be needing to do is ideally what they do every day when the when you 153 00:11:59,410 --> 00:12:00,210 are using GitHub. 154 00:12:00,430 --> 00:12:05,970 So just go to your code and the pool, whatever has been, whatever the rest of the team have done. 155 00:12:06,310 --> 00:12:08,410 So, for instance, you can just do get pool. 156 00:12:10,030 --> 00:12:15,130 When you do get the pool, this thing is going to go ahead in the pool or everything that the rest of 157 00:12:15,130 --> 00:12:21,460 the team have pushed to your repository online, and then when the code has to come here, remember, 158 00:12:21,460 --> 00:12:27,220 we have we have you you need to do it migrates, not get back into my grid. 159 00:12:27,640 --> 00:12:32,320 So that is the code that the rest of the team have done can be reflected into your database. 160 00:12:32,890 --> 00:12:39,040 So if, for instance, you had three or four team members, one of the team members working on this 161 00:12:39,700 --> 00:12:46,380 there is working on one of the team members is working on the article duct tape. 162 00:12:47,050 --> 00:12:48,840 The other one is working on membership. 163 00:12:48,850 --> 00:12:50,830 The other one is working on member. 164 00:12:50,840 --> 00:12:55,560 The other one is working on so many other things that would be working on every time, something once, 165 00:12:55,700 --> 00:12:58,780 just like you use getting all the others off their projects. 166 00:12:58,780 --> 00:13:03,990 Every time you finish something, push it only to get when you push end to end. 167 00:13:04,000 --> 00:13:10,060 And the other thing that you may be needing to do is to manage your repository with the different branches. 168 00:13:10,390 --> 00:13:16,540 So let let let don't put push everything to the main branch that we have created here. 169 00:13:16,870 --> 00:13:19,180 You see, I was the only one branch for now. 170 00:13:19,510 --> 00:13:23,590 So let every team member, for instance, have a branch. 171 00:13:23,590 --> 00:13:29,740 So if you have one person working on articulable, you have a branch for Artecoll Library that is managing 172 00:13:29,740 --> 00:13:35,800 everything to do that, then the next team member may be working on library membership, have a branch 173 00:13:35,800 --> 00:13:43,930 for that, and then maybe have one one one team member who pushes all the code that you have in all 174 00:13:43,930 --> 00:13:48,990 the branches and imagines it to the mean to the main main branch here. 175 00:13:49,840 --> 00:13:51,160 Let me give you an example. 176 00:13:51,400 --> 00:13:52,510 Let me go back home. 177 00:13:53,260 --> 00:13:56,410 I have I have a team here. 178 00:13:57,580 --> 00:13:59,710 You can see the projects that we have here. 179 00:14:00,430 --> 00:14:06,370 And I can if I go, for instance, to see custom of. 180 00:14:09,280 --> 00:14:14,680 The branches that we have here, if I go to to request this one, doesn't have a pull request, if I 181 00:14:14,680 --> 00:14:19,150 go to these branches, you see this one has three branches. 182 00:14:19,660 --> 00:14:21,030 I can view all branches. 183 00:14:21,580 --> 00:14:24,780 There is a future here for export use are all permissions. 184 00:14:24,970 --> 00:14:29,480 So everything about user permissions is managed with this branch. 185 00:14:29,950 --> 00:14:33,260 Everything on this is that one of the team members is called thuggishness. 186 00:14:33,730 --> 00:14:39,940 Everything that the issue is doing, he is using all his code here and then I am the only one who can 187 00:14:39,940 --> 00:14:43,080 mudd's everything that they do into the main branch here. 188 00:14:43,780 --> 00:14:45,800 So you may be needing to do that as well. 189 00:14:45,800 --> 00:14:54,340 On you up so late, every feature you work on be pushed to a specific branch and then have one team 190 00:14:54,340 --> 00:15:02,650 member managing everything from that branch to the other branches that I'm into the main branch of your 191 00:15:02,650 --> 00:15:03,300 application. 192 00:15:04,420 --> 00:15:06,400 I don't know that you have any questions up to that point. 193 00:15:11,510 --> 00:15:14,420 So you did get pulled? 194 00:15:14,450 --> 00:15:16,270 Yes, go ahead, go ahead. 195 00:15:16,370 --> 00:15:24,000 Sorry, but so I up to be patient in the database. 196 00:15:24,110 --> 00:15:27,040 How can we manage working on the same system? 197 00:15:29,600 --> 00:15:31,760 So the database will certainly be. 198 00:15:32,170 --> 00:15:34,870 You are looking at one database, Mohammed. 199 00:15:34,880 --> 00:15:39,280 I am hopeful that you are doing your development locally. 200 00:15:39,530 --> 00:15:39,800 Right. 201 00:15:44,280 --> 00:15:47,160 Is it remote or is it local, the development environment? 202 00:15:49,230 --> 00:15:53,380 Not no, a remote remote is remote. 203 00:15:54,990 --> 00:15:59,770 OK, OK, why are you doing it remotivate, why don't you do it for the local machines? 204 00:16:03,710 --> 00:16:08,300 Because we have a server, we have to push our work, the. 205 00:16:13,060 --> 00:16:19,840 Must it go that way, because my thinking would be my thinking would be you do the development on local 206 00:16:19,840 --> 00:16:28,150 machines, you may have a development Savar years where you push all you code and then that development 207 00:16:28,160 --> 00:16:36,460 server maybe can have you can you can do automated automated scripts and get on GitHub, where every 208 00:16:36,460 --> 00:16:44,550 time you push new code to GitHub, GitHub automatically deploys that code to yourself only because in 209 00:16:44,560 --> 00:16:51,040 my thinking, in my experience tells me that developing on a remote server can have a lot of downsides, 210 00:16:51,820 --> 00:16:58,660 because if one person, maybe, for instance, does something wrong or something that can break the 211 00:16:58,660 --> 00:17:04,060 code, the whole of the rest of the team, we have to wait for that thing to be resolved before you 212 00:17:04,060 --> 00:17:04,670 can move on. 213 00:17:05,170 --> 00:17:09,410 But if, for instance, you move, Mohammod, you are working on your machine. 214 00:17:09,760 --> 00:17:11,760 This in My Me is one of your team members. 215 00:17:11,770 --> 00:17:15,340 He is working on his machine and I and someone else. 216 00:17:15,850 --> 00:17:18,160 If you break your code, you break your machine. 217 00:17:18,160 --> 00:17:22,150 Only if you break his machine, you only break his machine. 218 00:17:23,230 --> 00:17:24,200 Break this over. 219 00:17:26,980 --> 00:17:29,500 OK, I understand your point. 220 00:17:31,000 --> 00:17:32,950 I think the question 221 00:17:35,680 --> 00:17:43,600 then the question is development, ERP next environment, where next you have installed it in your local 222 00:17:43,600 --> 00:17:44,250 machine. 223 00:17:44,260 --> 00:17:55,300 I mean, in your opinion, if it is installed in your laptop is at the beginning, we are urban in our 224 00:17:55,300 --> 00:17:59,910 machine, then we have to it in a remote server, you see. 225 00:18:02,230 --> 00:18:04,600 So not now it is in remote server. 226 00:18:05,980 --> 00:18:11,760 I know while working in a remote server in the future, yes. 227 00:18:13,320 --> 00:18:16,560 So what what what are you seeing Karani now? 228 00:18:16,560 --> 00:18:24,570 He's saying you have to keep IRP next in your local machine, in your laptop. 229 00:18:25,580 --> 00:18:36,800 Then you make a folder in GitHub with your name, then from your local machine, you will pull all codes 230 00:18:36,800 --> 00:18:39,140 from GitHub to your local machine. 231 00:18:40,220 --> 00:18:48,020 So you are your local machine will get all updates from other team members every morning, every morning, 232 00:18:48,230 --> 00:18:51,660 all of you, you will do get pulled. 233 00:18:52,280 --> 00:19:04,610 So in 9:00 morning, all of you, they have the same coach locally as if we're looking like that at 234 00:19:04,610 --> 00:19:05,080 this moment. 235 00:19:05,270 --> 00:19:05,910 At this moment. 236 00:19:06,260 --> 00:19:10,990 So it was supposed to finish you finish your work, your work today. 237 00:19:11,000 --> 00:19:15,770 You have something called you prepare and it is ready for the press. 238 00:19:17,280 --> 00:19:19,890 You will do push get pushed. 239 00:19:19,890 --> 00:19:26,030 You will move it to get folder in your branch, in your branch. 240 00:19:27,580 --> 00:19:34,420 OK, yes, guess so, and yeah, go ahead, you. 241 00:19:36,560 --> 00:19:47,190 When we create a GitHub repository, I think we we have we are able to push only our application, not 242 00:19:47,330 --> 00:19:49,140 the whole of the ERP. 243 00:19:53,020 --> 00:19:59,170 There's no point of pushing the whole of Europe because Europe needs to keep updating and you may be 244 00:19:59,170 --> 00:20:06,220 needing to keep updating your instance also there isn't could just track the application you have created. 245 00:20:07,750 --> 00:20:12,640 So let me let me let me let me let me emphasize this point here so that you get. 246 00:20:14,620 --> 00:20:20,890 The first thing you're going to do is create a report on GitHub, then push, for instance, you are 247 00:20:20,890 --> 00:20:26,470 the team leader there or whoever is your team leader, do that so that the rest of the team will just 248 00:20:26,470 --> 00:20:29,100 need to pull from what is here to get started. 249 00:20:29,380 --> 00:20:36,010 So on your local machine, what you're going to do, create the apps or the apps that you may be needing, 250 00:20:36,850 --> 00:20:44,320 then you take the code, you take in every app, you push all those apps to GitHub. 251 00:20:45,070 --> 00:20:50,110 When you push those apps to GitHub, the rest of your team members, let's say, for instance, mammies 252 00:20:50,110 --> 00:20:56,620 in your team member Mamey will install Europea next door like we have done before on his local machine. 253 00:20:57,430 --> 00:21:03,310 And then he because we have added him to you, to these repositories, to the repository you have created 254 00:21:03,310 --> 00:21:03,880 on GitHub. 255 00:21:04,450 --> 00:21:10,440 What he will do is that he will pull the code that is on GitHub to his local machines. 256 00:21:10,930 --> 00:21:17,500 So when he does that, he will automatically be tracking all the apps you have on his local machines 257 00:21:17,500 --> 00:21:18,120 as well. 258 00:21:18,730 --> 00:21:24,370 And then as if, for instance, he is working on Article Braly up DOCTYPE. 259 00:21:25,480 --> 00:21:35,440 When something like this is to to to to create something that you need to avoid problems with GitHub. 260 00:21:36,870 --> 00:21:38,410 Everything, something is ready. 261 00:21:38,530 --> 00:21:42,670 Listen, for instance, mummy has created duct tape and he has tested it is working fine. 262 00:21:43,050 --> 00:21:49,200 Don't wait for tomorrow morning, push it to GitHub then as if Mohammed, for instance, Mohammed, 263 00:21:49,200 --> 00:21:51,900 you are working on a library. 264 00:21:51,900 --> 00:21:57,330 Remember, DOCTYPE before you push, you are called whatever you have that you are on your local machine 265 00:21:57,540 --> 00:22:03,030 and it is working every time, even if it is at the middle of the day before you push this thing to 266 00:22:03,030 --> 00:22:08,520 GitHub, make sure you have food, just to be sure that you have the latest food that is on GitHub, 267 00:22:08,520 --> 00:22:09,450 on your local machine. 268 00:22:09,780 --> 00:22:11,130 So run get the pool. 269 00:22:11,550 --> 00:22:17,520 And then when that succeeds, run, get through so that you know, you are going to be pushed to the 270 00:22:17,520 --> 00:22:18,500 GitHub repository. 271 00:22:18,930 --> 00:22:24,570 And then the next day, mummy maybe has detected something on whatever maybe this app has been working 272 00:22:24,570 --> 00:22:24,870 on. 273 00:22:25,290 --> 00:22:31,020 The first thing he does is not get the first thing he does, even if it is, for instance, is the RPM 274 00:22:31,020 --> 00:22:37,050 in the evening, the first thing he will need to do is get the pool to get the code that is on this 275 00:22:37,050 --> 00:22:44,040 repository, on GitHub, onto his local machine, and then he will get the push to push that code online. 276 00:22:44,400 --> 00:22:50,170 So every time someone wants on something and it works on their local machine, the first step is get 277 00:22:50,180 --> 00:22:54,900 the pool and then get the push, get the pool and then get pushed. 278 00:22:54,900 --> 00:23:00,690 And that way you can have the code that is is remote synchronized to your local machines. 279 00:23:01,740 --> 00:23:03,240 I don't know that this career, Mohammed. 280 00:23:04,330 --> 00:23:22,600 But it's clear even when we we we we we change I doctype we will have an hour or an hour to be. 281 00:23:25,490 --> 00:23:25,770 Tony. 282 00:23:27,460 --> 00:23:42,520 When we do some modification and some that we will have our modification in our database or on our code, 283 00:23:44,080 --> 00:23:45,430 it is on your code. 284 00:23:46,750 --> 00:23:52,920 Let's say, for instance, let's say, for instance, you have this DOCTYPE and it was, you know, 285 00:23:52,930 --> 00:23:56,370 and you say this duct tape on your local machine to keep up with the Busia. 286 00:23:57,840 --> 00:24:04,590 If so, in your database is updated, Europeanist will also track these changes on their files, on 287 00:24:04,590 --> 00:24:05,350 our files here. 288 00:24:06,120 --> 00:24:14,140 Then when you push to get Hub, it will push whatever changes are on these files and then money is a 289 00:24:14,160 --> 00:24:15,060 part of your team. 290 00:24:15,390 --> 00:24:18,030 He will go to GitHub and the pool, the. 291 00:24:19,020 --> 00:24:23,600 So when he pulls these things that will come and write a rewrite these files. 292 00:24:23,620 --> 00:24:23,880 Yes. 293 00:24:24,060 --> 00:24:26,300 Somehow some files will have to be changed. 294 00:24:26,820 --> 00:24:34,500 And then when he does that, he will push the code also online and then the next commander will be needing 295 00:24:34,500 --> 00:24:37,450 to run just to be safe for the sake of being extended for up. 296 00:24:37,500 --> 00:24:43,110 It is bent migrate what it to migrate, does it check their files? 297 00:24:43,770 --> 00:24:46,020 And that may be needing to increase this font a little bit. 298 00:24:46,880 --> 00:24:55,810 If you check their files for any changes that are unthreatened in the database and then it saves them 299 00:24:55,820 --> 00:24:57,260 all the changes to your database. 300 00:24:57,710 --> 00:25:00,560 We are using locally and that's it. 301 00:25:00,800 --> 00:25:05,600 And then you can remember you can use all your remote in any instance. 302 00:25:05,990 --> 00:25:12,800 You can write an automated script so that every time someone pushes through this repository, you don't 303 00:25:12,800 --> 00:25:19,340 have to go to to go to the remote, remote and sarva and to get the pool, but also in the remote Savar, 304 00:25:19,340 --> 00:25:24,830 using, as they say, you can do it manually by going to a switching to your remote environment and 305 00:25:24,830 --> 00:25:27,180 then get the pool and then Benchemsi grid. 306 00:25:27,350 --> 00:25:31,490 You can also do that just like anyone will be doing it in their local machines here. 307 00:25:32,000 --> 00:25:37,790 But again, those are things that you can automate GitHub ways of automating those scripts so that every 308 00:25:37,790 --> 00:25:44,540 time there is something that has been posted here, it will take place and deploy that to your remote 309 00:25:44,690 --> 00:25:45,270 server. 310 00:25:45,500 --> 00:25:50,780 So it is up to you and your team to decide whether you want it is being automated or maybe you are team 311 00:25:50,780 --> 00:25:52,220 leader can be doing that. 312 00:25:52,220 --> 00:25:54,250 Maybe at the end of the day. 313 00:25:54,260 --> 00:26:03,320 At the end of the day, it is helpful to see the future Karani because we are really working a lot with 314 00:26:05,960 --> 00:26:06,710 the GitHub one. 315 00:26:08,130 --> 00:26:09,210 No, no, no. 316 00:26:09,530 --> 00:26:15,840 I told you that we have to see the pictures, the model of picture. 317 00:26:17,030 --> 00:26:18,610 Yeah, yeah, yeah. 318 00:26:19,100 --> 00:26:21,030 This one is on the whoops. 319 00:26:21,050 --> 00:26:22,290 Yeah, yeah. 320 00:26:22,850 --> 00:26:25,000 Yes we will. 321 00:26:25,490 --> 00:26:26,270 Yes we will. 322 00:26:26,270 --> 00:26:27,970 Working a lot with pictures. 323 00:26:29,030 --> 00:26:30,920 Yeah I understand they are fixed justice. 324 00:26:30,920 --> 00:26:33,350 I think fictious is another topic somewhere. 325 00:26:34,400 --> 00:26:35,150 Can we have it. 326 00:26:36,410 --> 00:26:36,860 We don't have. 327 00:26:36,900 --> 00:26:37,100 Yeah. 328 00:26:37,100 --> 00:26:38,600 OK was talking Mohammed. 329 00:26:38,600 --> 00:26:39,470 I get it. 330 00:26:39,980 --> 00:26:44,120 We will Mummy and I will look into that and then we will see how we can fix that. 331 00:26:45,670 --> 00:26:46,130 Yes. 332 00:26:46,550 --> 00:26:54,110 Because we told us that we will see it in the advanced topic, how we work, how we will work with fixing. 333 00:26:55,220 --> 00:26:55,490 Yeah. 334 00:26:55,580 --> 00:26:55,900 Fixed. 335 00:26:55,970 --> 00:26:56,390 I agree. 336 00:26:56,390 --> 00:26:58,360 Features fixed will come in very handy. 337 00:26:58,490 --> 00:26:59,960 In that case we are. 338 00:27:00,350 --> 00:27:01,550 OK Mummy. 339 00:27:01,550 --> 00:27:02,870 Will we organise that. 340 00:27:04,590 --> 00:27:05,370 OK, thank you. 341 00:27:05,810 --> 00:27:07,110 Sure, we will. 342 00:27:07,380 --> 00:27:13,110 I took notes about the picture I have questioned now. 343 00:27:13,130 --> 00:27:16,770 You said every time before pushing you to pull right. 344 00:27:16,860 --> 00:27:17,500 Get pulled. 345 00:27:18,030 --> 00:27:28,200 So when you get you do get pulled to retrieve the changes from the repository to your local machine. 346 00:27:28,590 --> 00:27:36,640 So after get pulled, you have to do Benchmade migrate before get push or not required. 347 00:27:38,110 --> 00:27:43,930 No, it is not required to do Benchemsi great before get get pushed, because ideally when you get the 348 00:27:43,930 --> 00:27:47,920 pool, you are going to be in some way the code. 349 00:27:47,950 --> 00:27:55,330 That is only if there are any changes that are are on on your local instance, GitHub is going to pull 350 00:27:55,330 --> 00:27:58,090 those things and and update your files. 351 00:27:58,480 --> 00:28:01,030 So bench migrate is ideally for the database. 352 00:28:01,030 --> 00:28:02,140 So you don't need to do that. 353 00:28:02,710 --> 00:28:08,770 The reason why we need to do get pool before we get pushed is to avoid conflicts, because there may 354 00:28:08,770 --> 00:28:14,640 be someone who has seen the file that you have worked on and did not want a conflict to occur online. 355 00:28:14,980 --> 00:28:20,830 If you have a conflict, you are going to need to resolve to to do to know that you had a conflict on 356 00:28:20,830 --> 00:28:24,880 your local machine and therefore the rest of the team can continue without any problems. 357 00:28:25,300 --> 00:28:31,140 So what is going to happen is when you get the pool and maybe you had worked on the same file with some 358 00:28:31,140 --> 00:28:35,920 other team member, you are going to have a conflict locally and then you are going to resolve that 359 00:28:35,920 --> 00:28:38,100 conflict and then get pushed clean food. 360 00:28:38,140 --> 00:28:40,800 That is not going to cause any issues only. 361 00:28:42,160 --> 00:28:51,380 So here, Deadpool will merge implicitly, a merger will happen right, with good. 362 00:28:51,630 --> 00:28:53,780 Yes, yes, yes, yeah, yeah. 363 00:28:53,800 --> 00:28:55,170 You are going to have your fans updated. 364 00:28:55,240 --> 00:28:55,490 Yes. 365 00:28:56,800 --> 00:29:07,270 But if you want to see the the new code which you have imported or in your local machine, you have 366 00:29:07,270 --> 00:29:15,490 to do well, some regret because it is still a file only so that your database like you mean you you 367 00:29:15,490 --> 00:29:22,820 have to install those new codes in your database to see the if you want to test, right. 368 00:29:23,740 --> 00:29:24,280 Yes. 369 00:29:24,960 --> 00:29:25,230 Yes. 370 00:29:25,240 --> 00:29:25,540 Yes. 371 00:29:27,630 --> 00:29:30,350 Yeah, um, OK. 372 00:29:34,900 --> 00:29:38,590 Yeah, good, so can we. 373 00:29:38,730 --> 00:29:40,180 OK, do we have any other question? 374 00:29:40,180 --> 00:29:42,700 Is there anything else that we need to do on GitHub? 375 00:29:44,230 --> 00:29:48,730 You know, any anyone else with suspicion before you can move on to the next topic? 376 00:29:49,420 --> 00:29:57,910 Yes, maybe a small question on the are you always using a get comment line or you have some Refco? 377 00:30:01,900 --> 00:30:03,070 Personally, I do. 378 00:30:03,070 --> 00:30:03,430 I do. 379 00:30:03,430 --> 00:30:03,820 I do. 380 00:30:03,820 --> 00:30:04,150 I do. 381 00:30:04,150 --> 00:30:10,120 I normally use the command line here, but I have some other people on my team that use this. 382 00:30:10,120 --> 00:30:13,890 I blame not to things, but this could bring this one here. 383 00:30:14,230 --> 00:30:15,050 Is it somewhere. 384 00:30:15,070 --> 00:30:16,810 There is somewhere that we have this one. 385 00:30:16,990 --> 00:30:17,770 We have GitHub. 386 00:30:17,770 --> 00:30:18,520 So you can track that. 387 00:30:18,520 --> 00:30:19,400 You can do everything. 388 00:30:19,420 --> 00:30:23,500 Also on this note, I mean, this this tool here. 389 00:30:25,660 --> 00:30:26,320 OK, good. 390 00:30:26,350 --> 00:30:26,730 Thank you. 391 00:30:28,930 --> 00:30:29,330 OK. 392 00:30:30,230 --> 00:30:35,200 What famous mistake, we should avoid working with it. 393 00:30:36,460 --> 00:30:42,260 We have conflicts, conflicts, pushing, pushing code before you pull. 394 00:30:42,680 --> 00:30:48,600 What happens if maybe someone has done something and then you go and push some? 395 00:30:48,870 --> 00:30:55,670 Some sometimes you can override someone's code and you find that maybe some some features that you thought 396 00:30:55,670 --> 00:30:58,100 you had complete that you had worked on completely. 397 00:30:58,620 --> 00:31:04,760 When you come to, you find that those things are not done and you do realize that it is because someone 398 00:31:04,760 --> 00:31:08,740 get pushed before they pulled what was already done and closed only. 399 00:31:09,170 --> 00:31:16,040 So it is very, very critical to always as a team get pulled before you can push what you have done 400 00:31:16,060 --> 00:31:16,340 only. 401 00:31:18,880 --> 00:31:27,340 So if I understand very well, so before doing a custom app or for any new custom app, I have to create 402 00:31:28,270 --> 00:31:32,090 a separate folder or repository for that customer. 403 00:31:32,120 --> 00:31:32,470 Right. 404 00:31:34,990 --> 00:31:37,050 Well, and get 405 00:31:39,540 --> 00:31:41,250 in and get. 406 00:31:41,330 --> 00:31:46,050 Yes, yes, yes, you have to create a new repository for every app. 407 00:31:46,840 --> 00:31:47,280 Yes. 408 00:31:48,090 --> 00:31:56,490 And under that repository I have many branches, so I have main branch and different branches. 409 00:31:57,080 --> 00:31:57,880 Yes. 410 00:31:57,900 --> 00:31:58,350 Yes. 411 00:31:58,350 --> 00:32:04,200 Every feature you are working on, the idea is create a branch for it so that you can track it changes 412 00:32:04,200 --> 00:32:05,250 on that branch. 413 00:32:05,730 --> 00:32:11,430 The other reason is the other reason is you don't want to be pushing everything on the main branch, 414 00:32:12,060 --> 00:32:18,060 have a separate branch so that in case you have a problem, you can roll back just one branch instead 415 00:32:18,060 --> 00:32:24,810 of having an issue on the Letterman branch manager code that is tried and tested. 416 00:32:25,650 --> 00:32:29,790 OK, now suppose a new team member joined. 417 00:32:30,210 --> 00:32:33,750 OK, you have to join in in the middle. 418 00:32:34,080 --> 00:32:40,050 OK, so now he will install ERP next in his machine. 419 00:32:41,610 --> 00:32:45,140 Then he will do get to pull, right. 420 00:32:46,020 --> 00:32:46,470 Correct. 421 00:32:47,190 --> 00:32:55,120 He will do get all and get merged and not get merged. 422 00:32:55,130 --> 00:32:56,250 Events migrate. 423 00:32:56,790 --> 00:32:57,290 Correct. 424 00:32:57,300 --> 00:32:58,140 Absolutely correct. 425 00:32:58,470 --> 00:33:00,090 So we do benchmark right now. 426 00:33:00,180 --> 00:33:03,200 He will start at the same level as the other teams. 427 00:33:03,790 --> 00:33:04,240 Correct. 428 00:33:04,310 --> 00:33:04,440 Very. 429 00:33:05,550 --> 00:33:06,600 Once he finish. 430 00:33:07,800 --> 00:33:10,970 Suppose you create for his features a new branch. 431 00:33:10,980 --> 00:33:12,870 He will create a new branch locally. 432 00:33:13,440 --> 00:33:17,400 Then he will do get to push. 433 00:33:17,760 --> 00:33:21,000 So this could enter his local branch. 434 00:33:21,310 --> 00:33:24,550 It will be transferred to get in his branch also. 435 00:33:24,810 --> 00:33:34,520 So when he when he do get the get push automatically, a new branch get created in the repository, 436 00:33:34,530 --> 00:33:34,850 right? 437 00:33:35,520 --> 00:33:35,990 Yes. 438 00:33:36,610 --> 00:33:36,970 Yes. 439 00:33:37,390 --> 00:33:41,580 When you have changes, what you're going to do here when you are pushing is that you're going to check 440 00:33:41,580 --> 00:33:48,190 out a new branch to get checked out and you are brines and then you are going to put it out online. 441 00:33:48,210 --> 00:33:54,210 What was I going to do is that is going to have a branch here created automatic for you automatically, 442 00:33:54,300 --> 00:33:59,340 because ideally what happens is that GitHub would be managing those things locally. 443 00:33:59,670 --> 00:34:02,020 If you look at these files, the ones we have here. 444 00:34:02,370 --> 00:34:07,020 If I do LSP, we have gates. 445 00:34:07,170 --> 00:34:10,500 So this gate is tracking everything, including our branches. 446 00:34:10,860 --> 00:34:13,710 So when you check out a new branch, it is created inside. 447 00:34:13,710 --> 00:34:14,100 It is. 448 00:34:14,730 --> 00:34:17,400 And now everything we we get pushed. 449 00:34:17,400 --> 00:34:18,760 It pushes whatever is here. 450 00:34:19,200 --> 00:34:22,710 So this will go online and create a new branch for that. 451 00:34:23,770 --> 00:34:24,160 Great. 452 00:34:24,870 --> 00:34:27,660 So here we do this. 453 00:34:27,900 --> 00:34:28,650 Yes, sir. 454 00:34:29,700 --> 00:34:39,090 So most of the talking about cloning a project, cloning application, existing application, they say. 455 00:34:41,020 --> 00:34:48,730 How can we clone the application for four for a new a new developer or new user? 456 00:34:50,400 --> 00:34:55,130 It's exactly what mommy said, what you are going to do for the developer. 457 00:34:55,170 --> 00:35:02,430 You have to install on your local machine and then the next day, remember, you have you have all your 458 00:35:02,430 --> 00:35:06,620 branches here, all your apps, not branches, all your apps on GitHub. 459 00:35:06,930 --> 00:35:11,910 So just come to the branch and add the team member agility member here. 460 00:35:12,270 --> 00:35:14,600 And then what they are going to do is this. 461 00:35:14,630 --> 00:35:21,630 This is good to close to to to Karoonda, the repository when they clone it is going to go directly 462 00:35:21,630 --> 00:35:25,560 to their to in the apps section, in the app section of your application. 463 00:35:25,710 --> 00:35:29,120 I don't need that in the application of your application here. 464 00:35:29,670 --> 00:35:35,850 And then what we do need to do next, remember all the data, the database tables that are on those 465 00:35:35,850 --> 00:35:39,630 apps are not right on the local instance of the machines. 466 00:35:39,840 --> 00:35:43,170 So they will need to do Benchemsi grid so that they can be updated. 467 00:35:43,680 --> 00:35:48,180 Once they do that, they are going to go there will be at the same level with every other developer 468 00:35:48,180 --> 00:35:49,890 that are on that organization. 469 00:35:53,400 --> 00:35:53,910 Mohammed. 470 00:35:55,950 --> 00:35:57,280 OK, thank you. 471 00:35:58,370 --> 00:35:58,810 You're welcome. 472 00:35:59,160 --> 00:36:06,570 May I have something, Karenni, if you want to add Kloner existing customer, you need to use the what 473 00:36:06,900 --> 00:36:12,510 what he we use to install ERP Nexen Frappé, which is Bensch. 474 00:36:12,810 --> 00:36:14,520 Get up, I believe. 475 00:36:14,520 --> 00:36:19,520 And then you would put the link to your GitHub GitHub repository, right? 476 00:36:20,160 --> 00:36:20,910 Absolutely. 477 00:36:20,910 --> 00:36:21,990 That's that's another way. 478 00:36:21,990 --> 00:36:23,220 That's another way of doing it. 479 00:36:23,580 --> 00:36:24,420 We're doing it more. 480 00:36:24,460 --> 00:36:24,920 Yeah. 481 00:36:26,340 --> 00:36:26,720 Yeah. 482 00:36:27,630 --> 00:36:28,440 So I don't know whether. 483 00:36:28,440 --> 00:36:30,330 Mohammod, you got what Maureen is Issing. 484 00:36:33,640 --> 00:36:37,350 Because let me let you go, that you got what you said. 485 00:36:39,700 --> 00:36:48,690 Do think what what he is saying is, let me show you, if I do if I go to Europe next GitHub. 486 00:36:49,880 --> 00:36:55,610 What we normally do and we're installing a new app is bench new app, for instance, when you are installing, 487 00:36:56,180 --> 00:37:02,720 we normally do bench get up and then we give some link here where we normally give. 488 00:37:02,750 --> 00:37:08,650 Here is the link that is normally we normally give the link that is on this branch. 489 00:37:09,170 --> 00:37:12,930 So we normally get the apps from GitHub repository. 490 00:37:13,310 --> 00:37:22,160 So there is nothing that stops us from doing doing bench get up and then we give the link off our up 491 00:37:22,160 --> 00:37:24,610 here is nothing that stops us from doing that. 492 00:37:24,890 --> 00:37:26,230 So we can do that as well. 493 00:37:28,870 --> 00:37:29,810 Maureen, is that clear? 494 00:37:30,520 --> 00:37:32,500 I know Maureen, but Mohammed. 495 00:37:34,570 --> 00:37:35,480 Yes, I see. 496 00:37:35,560 --> 00:37:46,080 And when we will start an application for a customer or a client, how can we do it on? 497 00:37:47,880 --> 00:37:51,990 OK, will you be installing it on the on this, I suppose? 498 00:37:53,430 --> 00:37:53,970 This. 499 00:37:55,830 --> 00:38:02,820 So that is to mean you have developed your your application, it is finished, and now you need to maybe 500 00:38:02,820 --> 00:38:03,830 sell it to a customer. 501 00:38:05,270 --> 00:38:12,020 Yes, and assuming you are not selling it as a service, you will need to go and maybe install it on 502 00:38:12,020 --> 00:38:12,530 the Asaba. 503 00:38:12,680 --> 00:38:19,840 So what you need to do is Iosava, for instance, is just like another machine that is online. 504 00:38:20,510 --> 00:38:26,870 So the exact same way that your developer did when they came with your local machine is the exact same 505 00:38:26,870 --> 00:38:28,970 way you can do on that Savar that these remote. 506 00:38:32,110 --> 00:38:33,100 OK, I see. 507 00:38:35,720 --> 00:38:37,850 Good to see you. 508 00:38:37,890 --> 00:38:38,420 Thank you. 509 00:38:40,700 --> 00:38:53,360 OK, Kiran, if you don't mind, I am more confortable if you do an example of get push, get pull now. 510 00:38:53,540 --> 00:39:02,660 Now, if you you do development and it is a small thing, you tested locally at your level. 511 00:39:03,200 --> 00:39:10,030 But if you have another big project, OK, you have another instance which is called the test instance 512 00:39:10,040 --> 00:39:17,610 or whatever, there is another instance called for instance or staging and before deploy in production. 513 00:39:17,900 --> 00:39:21,590 So all this I cannot repeat. 514 00:39:21,590 --> 00:39:26,090 Now, if I repeated this, this is the decision. 515 00:39:26,900 --> 00:39:28,370 I cannot do it myself. 516 00:39:29,180 --> 00:39:37,070 So if you write comments in front of us and tell you this is the step one, step two, step three from 517 00:39:37,070 --> 00:39:41,390 the pull to push to deploy in production. 518 00:39:45,780 --> 00:39:47,650 Deploying production is something tricky. 519 00:39:47,670 --> 00:39:54,330 We are you know, when you say deploying production, I'm assuming we have a production sarva so I am 520 00:39:54,330 --> 00:39:55,200 going to maybe I can. 521 00:39:55,220 --> 00:39:57,780 What I can do is we change our file. 522 00:39:57,930 --> 00:40:00,750 For instance, we can come here and change something. 523 00:40:00,900 --> 00:40:01,070 What. 524 00:40:01,200 --> 00:40:05,400 No one, no one is going this. 525 00:40:05,850 --> 00:40:07,230 If we do, if we do not. 526 00:40:07,570 --> 00:40:08,270 I'm used to this. 527 00:40:08,490 --> 00:40:16,510 If we do get status here which is used to check whether maybe you have to see this when you are on your 528 00:40:16,620 --> 00:40:17,160 machine. 529 00:40:17,910 --> 00:40:21,310 This one is telling us that our director is clean. 530 00:40:21,330 --> 00:40:23,340 We don't have any untracked files. 531 00:40:23,760 --> 00:40:26,340 If we come here and change something, even if we are. 532 00:40:26,440 --> 00:40:31,470 Did you take this message to these are skiddy text message. 533 00:40:32,490 --> 00:40:38,880 And we say, if not, this is utils file and you see the fact the color of this one has changed, this 534 00:40:38,880 --> 00:40:40,160 is this is very good. 535 00:40:40,410 --> 00:40:43,680 And also here what Maureen was asking this. 536 00:40:43,690 --> 00:40:44,930 This thing has changed here. 537 00:40:45,240 --> 00:40:49,530 So if you are not comfortable with the command line, you can even push it from here and it will go 538 00:40:49,530 --> 00:40:49,900 online. 539 00:40:50,520 --> 00:40:55,830 So this one really is showing you that this file is untracked and it is also showing us on this line 540 00:40:55,830 --> 00:40:57,150 what exactly has changed. 541 00:40:57,900 --> 00:41:02,700 If I come to my command line here, I can do I can now run this employment status. 542 00:41:02,940 --> 00:41:07,430 And this will be showing me that this this particular file is on trust. 543 00:41:07,860 --> 00:41:13,380 So you see, when we ran this against us initially, what we saw is that our country is clean when we 544 00:41:13,380 --> 00:41:13,760 run it. 545 00:41:13,770 --> 00:41:16,800 Now, after changing this file, it's telling us this file is not structured. 546 00:41:17,310 --> 00:41:24,630 The next thing, if you are amandola in person, is to just get Guitard and then you can give the product 547 00:41:24,630 --> 00:41:25,260 to this file. 548 00:41:25,260 --> 00:41:27,570 So I can just see I want to add library. 549 00:41:28,810 --> 00:41:36,900 So this one has to that's why it is doing this, so I can do library management and spelling of good 550 00:41:37,000 --> 00:41:39,760 first round of it. 551 00:41:40,470 --> 00:41:40,760 Yeah. 552 00:41:41,260 --> 00:41:42,650 So I can do that. 553 00:41:42,670 --> 00:41:44,530 So this is good advice. 554 00:41:44,890 --> 00:41:47,260 And then I enter that one has been added. 555 00:41:47,650 --> 00:41:50,920 Now, if I do, I run the same command again with us. 556 00:41:51,460 --> 00:41:56,300 This is green and that means this one has now been added to our remote, to our local. 557 00:41:57,190 --> 00:42:00,010 The next thing is to get a comet. 558 00:42:00,880 --> 00:42:02,500 It comet will come with a message. 559 00:42:02,510 --> 00:42:07,270 You need to provide a message because every every everything you commit online will have. 560 00:42:07,570 --> 00:42:11,560 You need to explain to the team members what exactly have you done? 561 00:42:11,570 --> 00:42:12,430 What are you pushing on? 562 00:42:12,440 --> 00:42:19,120 Like I can say, this is our test for GitHub, but you're are going to be giving meaningful messages 563 00:42:19,120 --> 00:42:19,390 here. 564 00:42:20,940 --> 00:42:27,930 And the biggest one I would ask me that one final has been added and then anything is just that it is 565 00:42:27,930 --> 00:42:28,260 gone. 566 00:42:28,860 --> 00:42:32,760 Oh, sorry, I need to provide my my username. 567 00:42:35,140 --> 00:42:36,050 What is my password? 568 00:42:36,120 --> 00:42:36,450 OK. 569 00:42:39,230 --> 00:42:39,790 That's it. 570 00:42:40,840 --> 00:42:48,880 So not one has been put online and now let me clear this to create room clear if now I come here and 571 00:42:49,390 --> 00:42:54,100 get status again, this is telling me that my writing is clean. 572 00:42:54,100 --> 00:42:55,730 So everything has been pushed online. 573 00:42:56,050 --> 00:42:57,670 Now, if I come online. 574 00:42:59,750 --> 00:43:06,970 If I come online to my to my repository here and I go, he is not in it was utils. 575 00:43:06,980 --> 00:43:07,190 Yeah. 576 00:43:07,190 --> 00:43:10,490 This one, I will find out the message I put. 577 00:43:10,490 --> 00:43:11,540 I change something here. 578 00:43:12,080 --> 00:43:12,410 Yeah. 579 00:43:12,440 --> 00:43:12,820 This one. 580 00:43:12,830 --> 00:43:13,740 This is what we added. 581 00:43:13,760 --> 00:43:15,440 So this one has been pushed online now. 582 00:43:15,470 --> 00:43:22,450 So any other developer who will be needing to be doing it cool will have this line updated on the machines 583 00:43:22,460 --> 00:43:22,940 as well. 584 00:43:25,100 --> 00:43:25,970 Are you comfortable now? 585 00:43:26,600 --> 00:43:27,170 Yes. 586 00:43:27,560 --> 00:43:27,980 Now. 587 00:43:27,980 --> 00:43:30,540 Now you push to get right? 588 00:43:31,650 --> 00:43:32,260 Yes. 589 00:43:32,280 --> 00:43:32,630 Yes. 590 00:43:33,500 --> 00:43:35,420 Now I want to deploy this. 591 00:43:36,020 --> 00:43:38,320 This changes into production. 592 00:43:39,170 --> 00:43:45,470 So that is why I said that is that is money that is outside of the scope of this training. 593 00:43:45,890 --> 00:43:47,010 But what you can do, No. 594 00:43:47,010 --> 00:43:55,160 One, the production instance has Iosava so that the sarva treated just like that is when you are doing 595 00:43:55,160 --> 00:44:00,770 it manually treated like any other computer you have when you are local development team. 596 00:44:01,220 --> 00:44:09,710 So S.H. into your server and then get the pool, just go to the to the Tamino and get the pool and then 597 00:44:09,710 --> 00:44:11,540 when to migrate you are done. 598 00:44:12,350 --> 00:44:23,600 Alternatively, first you look to the you log in the production server, Linux user and the production 599 00:44:23,600 --> 00:44:24,000 server. 600 00:44:24,710 --> 00:44:31,760 OK, so you go to the best user and go to the application. 601 00:44:33,200 --> 00:44:37,940 As he said, Maureen, you have to create custom, right? 602 00:44:37,940 --> 00:44:40,340 You have to do all these steps. 603 00:44:40,340 --> 00:44:47,150 If you are moving the custom up from development to production, you have to create this app, install 604 00:44:47,150 --> 00:44:47,590 the app. 605 00:44:47,630 --> 00:44:49,910 All these steps need to be done before. 606 00:44:49,910 --> 00:44:50,320 Right. 607 00:44:50,930 --> 00:44:52,790 It's not part of the steps. 608 00:44:54,510 --> 00:45:00,780 No, it's no good steps, and you are when you have it on GitHub, you don't need to create you don't 609 00:45:00,780 --> 00:45:02,340 need to create an app. 610 00:45:02,790 --> 00:45:05,840 You are just getting it from GitHub and that's it. 611 00:45:05,850 --> 00:45:07,770 And then you install it on your machine. 612 00:45:07,800 --> 00:45:08,850 I mean, on your server. 613 00:45:09,870 --> 00:45:17,010 And that is only so that is only for the first time, the other things, you will be just going online 614 00:45:17,010 --> 00:45:21,090 and then get pool and then Benchemsi. 615 00:45:21,100 --> 00:45:21,960 Great and you are done. 616 00:45:23,040 --> 00:45:28,800 OK, can you open a text file or Excel sheet and tell me the right steps? 617 00:45:28,800 --> 00:45:31,060 There takes time. 618 00:45:32,880 --> 00:45:35,040 OK, takes to find text. 619 00:45:35,340 --> 00:45:35,750 Which one. 620 00:45:35,780 --> 00:45:40,850 Now can I or I can write them on this here. 621 00:45:41,110 --> 00:45:41,500 Yeah. 622 00:45:41,550 --> 00:45:43,750 Right, right in the in there too. 623 00:45:44,320 --> 00:45:44,550 Yeah. 624 00:45:45,130 --> 00:45:55,170 I mean I know I have, I have an exercise to move, to move a custom application or a custom report 625 00:45:55,170 --> 00:45:59,370 or any customization from development to production. 626 00:45:59,580 --> 00:46:07,260 And this task any developer is doing on a daily basis, it is doing maybe every day you have to move 627 00:46:07,260 --> 00:46:09,510 something from development to production. 628 00:46:09,630 --> 00:46:09,970 Right. 629 00:46:10,830 --> 00:46:15,180 So now I am not clear for me what I have to do. 630 00:46:15,180 --> 00:46:15,990 First step. 631 00:46:16,500 --> 00:46:17,280 Next step. 632 00:46:17,730 --> 00:46:25,020 As you said, the first step you have to do get up, get up the first. 633 00:46:25,020 --> 00:46:27,070 That's the only for the first time. 634 00:46:28,050 --> 00:46:28,860 Yeah, yeah, yeah. 635 00:46:29,040 --> 00:46:30,720 This steps. 636 00:46:30,750 --> 00:46:32,850 Can you put it in context? 637 00:46:33,240 --> 00:46:38,620 Can you write it in this shot so anyone knows the steps overall. 638 00:46:39,000 --> 00:46:46,470 So if I say after the session I will do this exercise, I have to complete it alone. 639 00:46:46,890 --> 00:46:47,730 I have to do it. 640 00:46:47,730 --> 00:46:48,390 I can do it. 641 00:46:49,920 --> 00:46:51,570 So that's the first step. 642 00:46:52,140 --> 00:46:54,630 You get the up and then you install. 643 00:46:54,670 --> 00:47:00,750 So this will be based once again, you are saying, get in, get up. 644 00:47:00,750 --> 00:47:04,200 You are in the local machine now or you are in production. 645 00:47:05,230 --> 00:47:08,960 It never, ever bothered him both. 646 00:47:09,130 --> 00:47:09,630 OK? 647 00:47:09,680 --> 00:47:15,610 Yeah, yeah, yeah, so Bensch, yeah, this is this will be your side. 648 00:47:15,910 --> 00:47:25,600 So bench side we have side, then your side, then you need to do is pull up. 649 00:47:25,930 --> 00:47:28,930 Then you are up revenue growth. 650 00:47:30,730 --> 00:47:31,300 It's up. 651 00:47:32,180 --> 00:47:40,330 Yes, those are those are the first two things, if you will, those ones are done when those ones are 652 00:47:40,340 --> 00:47:40,600 done. 653 00:47:40,990 --> 00:47:42,100 This will come with everything. 654 00:47:42,340 --> 00:47:49,160 So now after that, if now you are tracking changes, someone has to go to GitHub as they search into 655 00:47:49,160 --> 00:47:49,810 us over. 656 00:47:50,120 --> 00:47:53,410 The thing is, is is get pool. 657 00:47:55,060 --> 00:48:02,860 And then after you get to the bench, my great bench, not be in my great yeah. 658 00:48:04,420 --> 00:48:06,480 OK, now I have a question. 659 00:48:06,790 --> 00:48:14,440 They get comment, you put you issue bit comment under which further under the application folder, 660 00:48:14,830 --> 00:48:25,990 the other Modula folder or under the bench folders, forget coming and up you go into your apps and 661 00:48:25,990 --> 00:48:28,390 you get into the app that you want to get. 662 00:48:28,900 --> 00:48:29,680 That's where you run. 663 00:48:29,890 --> 00:48:35,130 For instance, you see here we are on our app library management. 664 00:48:35,410 --> 00:48:37,030 This is where you do the bench. 665 00:48:37,210 --> 00:48:38,740 If you come here, they get commands. 666 00:48:38,740 --> 00:48:45,430 If you come here and do something like get pool this, you complain that get is no get depository that 667 00:48:45,440 --> 00:48:47,110 is initialised at that level. 668 00:48:47,890 --> 00:48:56,760 So you need to go into your app and then you get a good pool from there, whatever. 669 00:48:56,770 --> 00:48:57,010 Yeah. 670 00:48:57,010 --> 00:48:57,810 That's why you do it. 671 00:48:59,900 --> 00:49:02,090 So I have also put it out on the chart. 672 00:49:02,490 --> 00:49:04,890 Yes, now in the in the report. 673 00:49:04,980 --> 00:49:10,760 Now, we didn't see four report customs report to create a customs report. 674 00:49:10,770 --> 00:49:16,610 The same steps you have to create customs up or and then you create your report under that. 675 00:49:19,140 --> 00:49:23,360 Report, you mean you to add another repository repository? 676 00:49:23,400 --> 00:49:24,240 No, no, no, no, no. 677 00:49:25,530 --> 00:49:33,210 I mean a new report, a totally new report in application to a report like we did last time. 678 00:49:33,210 --> 00:49:34,470 Print format, right? 679 00:49:35,500 --> 00:49:35,930 Uh huh. 680 00:49:36,240 --> 00:49:38,640 We have customized the print format. 681 00:49:40,550 --> 00:49:45,440 So this customization, how you would move it from development to production. 682 00:49:45,770 --> 00:49:48,920 Is it using the comment or these different? 683 00:49:51,820 --> 00:49:52,460 The reports. 684 00:49:53,310 --> 00:49:56,510 Yes, print format, you remember, we have you. 685 00:49:56,530 --> 00:49:59,110 We did our custom print format. 686 00:49:59,350 --> 00:49:59,680 Yeah. 687 00:49:59,930 --> 00:50:02,830 That that one also will be tracked because it is part of it. 688 00:50:03,130 --> 00:50:05,240 It forms part of the code that we have here. 689 00:50:05,680 --> 00:50:10,870 So when you have it on GitHub and you pull it online and you run prints migrated to come with, it will 690 00:50:10,870 --> 00:50:12,040 come to come with that. 691 00:50:12,460 --> 00:50:14,950 And there is something else that Mohammed does mention. 692 00:50:14,950 --> 00:50:21,070 The fixtures fixtures will come in very handy when you when we are handling the same things that fixtures 693 00:50:21,070 --> 00:50:26,500 are going to do, like even move even the data that you have on your inside of the duct. 694 00:50:30,410 --> 00:50:37,450 So there are some questions that fixtures are going to be answering your money, your picture will plan, 695 00:50:37,460 --> 00:50:40,580 and we will plan this, fix your next topic. 696 00:50:41,300 --> 00:50:45,810 And coming up next, we are going to look at pictures. 697 00:50:45,830 --> 00:50:46,120 Yes. 698 00:50:46,350 --> 00:50:49,780 We'll take a look here. 699 00:50:50,030 --> 00:50:51,970 So here's your question. 700 00:50:51,980 --> 00:50:53,920 You have questions yourself. 701 00:50:55,400 --> 00:50:56,820 Hello, Karen. 702 00:50:56,900 --> 00:51:11,970 Can you please keep on writing comment lines to push to push our words, our culture from local to to 703 00:51:11,990 --> 00:51:13,370 remote repo? 704 00:51:18,450 --> 00:51:21,990 You said I keep writing book and the chat and the chat. 705 00:51:23,580 --> 00:51:24,030 Yes. 706 00:51:25,470 --> 00:51:31,230 It's not the same for similar to to any other project. 707 00:51:33,660 --> 00:51:41,420 There is no specific issue for, uh, for the European external. 708 00:51:44,250 --> 00:51:45,570 I'm not getting your question. 709 00:51:47,690 --> 00:51:59,300 Can you please keep on writing the command lines to push our code from local to remote repo? 710 00:52:01,620 --> 00:52:10,130 Jill, you just write GIMPLE, which is getting good from report to local branch. 711 00:52:10,220 --> 00:52:13,260 Margaret, it's not a good read. 712 00:52:13,500 --> 00:52:16,280 It's not the outcome, though. 713 00:52:16,300 --> 00:52:25,020 It's still many, many others comments to push out of the country from local to the remote. 714 00:52:26,120 --> 00:52:35,210 OK, so they are the same government lines for for any others project projects such. 715 00:52:35,420 --> 00:52:35,690 Yeah. 716 00:52:36,170 --> 00:52:42,800 Of ISP dot net is the same as it is the same year is the same. 717 00:52:44,730 --> 00:52:47,370 So can you continue, he said continue, right? 718 00:52:47,640 --> 00:52:49,740 So you did get pulled. 719 00:52:50,010 --> 00:52:51,300 So you do benchwarmer. 720 00:52:51,310 --> 00:52:51,690 Great. 721 00:52:52,110 --> 00:52:58,460 Now you lose your your your coding, your modification, then you are happy. 722 00:52:58,470 --> 00:53:02,370 You will do get Guitard, right, Karenin? 723 00:53:05,370 --> 00:53:08,940 Come and get it and no, no, no. 724 00:53:08,970 --> 00:53:14,670 Remember these steps forward to get whatever is on GitHub to your production is done. 725 00:53:16,320 --> 00:53:18,930 Get put this one for production, right? 726 00:53:19,500 --> 00:53:20,850 Yeah, we are getting code. 727 00:53:21,420 --> 00:53:23,190 This is an app that is on GitHub. 728 00:53:23,190 --> 00:53:23,880 We are given. 729 00:53:24,270 --> 00:53:27,560 Then we install it on our own, our production in server. 730 00:53:29,400 --> 00:53:30,310 Yeah, that's it. 731 00:53:30,420 --> 00:53:35,400 So these other things, in case now someone has done changes and you need to get it to the production 732 00:53:35,400 --> 00:53:37,740 server which already we are already. 733 00:53:37,740 --> 00:53:38,490 You did this. 734 00:53:38,700 --> 00:53:39,180 Yes. 735 00:53:39,210 --> 00:53:43,110 You now go inside and get full and eventually agreed to synchronize. 736 00:53:44,520 --> 00:53:49,560 So next time you do only get full and regrade, correct. 737 00:53:50,370 --> 00:53:51,060 Excellent. 738 00:53:51,060 --> 00:53:51,480 Excellent. 739 00:53:51,900 --> 00:53:59,880 Now, his question, he want to see in the chat with the get push the sequence of comments you have 740 00:53:59,880 --> 00:54:10,320 to issue when you are pushing code from local machine to GitHub, similarly to what we did in production 741 00:54:10,590 --> 00:54:10,910 code. 742 00:54:11,650 --> 00:54:15,840 And he want to put it in chat. 743 00:54:17,130 --> 00:54:18,670 So that will depend. 744 00:54:18,960 --> 00:54:25,590 That's why I don't want to put it here, because if I come here and do get Pooh's, remember, this 745 00:54:25,590 --> 00:54:30,210 command is pushing this command will push your code to the main branch. 746 00:54:30,870 --> 00:54:34,110 And remember, sometimes sometimes you mean you have branches. 747 00:54:34,110 --> 00:54:36,540 So you may need to specify where are you pushing. 748 00:54:36,990 --> 00:54:42,790 You may need to check out the branch that that that you have been working on before you push your code. 749 00:54:43,320 --> 00:54:47,010 So this is get get this is a wide topic. 750 00:54:47,010 --> 00:54:53,290 That is maybe someone is not comfortable with get the first of many to understand to get this is correct. 751 00:54:53,520 --> 00:54:53,660 Yeah. 752 00:54:54,060 --> 00:54:56,150 So I joined the meeting man. 753 00:54:56,160 --> 00:54:59,250 May be late to join later call today. 754 00:54:59,520 --> 00:55:05,760 So that's why he's not he didn't see this bench the get push. 755 00:55:08,010 --> 00:55:13,380 You can find it in the recording and if you have a question we'll take the next call. 756 00:55:14,810 --> 00:55:16,250 OK, ok. 757 00:55:17,110 --> 00:55:17,940 We have a question. 758 00:55:19,770 --> 00:55:20,190 Yes. 759 00:55:20,190 --> 00:55:23,220 There's a command bench update. 760 00:55:23,580 --> 00:55:30,150 Am I right that this command will issue the get pool and bench me great all. 761 00:55:31,080 --> 00:55:31,920 In one step. 762 00:55:35,360 --> 00:55:36,960 I am not sure. 763 00:55:36,980 --> 00:55:37,500 I'm not sure. 764 00:55:37,620 --> 00:55:47,420 Maureen, you never mentioned it, no, no, actually, we use VentureBeat for Air Phoenix, full air 765 00:55:47,420 --> 00:55:50,490 Phoenix, not for our customer. 766 00:55:50,630 --> 00:55:50,910 Right? 767 00:55:51,320 --> 00:55:53,600 I believe it does all the apps. 768 00:55:53,600 --> 00:56:00,520 It does get full bench Maigret and more steps for all the apps installed. 769 00:56:02,240 --> 00:56:11,510 But from from Frappé Frappé folder, not your folder, not it can be from the bench folder. 770 00:56:11,510 --> 00:56:16,250 It will, it will update all the apps installed in your bench. 771 00:56:17,720 --> 00:56:18,510 That makes sense. 772 00:56:18,870 --> 00:56:20,570 Mommy, mommy, what do you think makes sense? 773 00:56:20,570 --> 00:56:25,390 Because ideally we normally do that one I think is going to be here. 774 00:56:25,410 --> 00:56:33,800 My right bench appears as if if you are on this territory, you are able to access the director of apps. 775 00:56:33,810 --> 00:56:39,620 So I think somehow I have never used it myself, but I think somehow this thing can go into the apps 776 00:56:39,620 --> 00:56:46,520 directory and then look at all the apps you have and then go to get a pool or whatever is pulling and 777 00:56:46,520 --> 00:56:48,810 then migrate eventually agreed to them. 778 00:56:49,430 --> 00:56:50,100 I think so. 779 00:56:50,120 --> 00:56:52,580 I have never used it so we can explore to see what it does. 780 00:56:53,540 --> 00:56:57,860 But initially your apps doesn't know there is no link. 781 00:56:58,430 --> 00:57:08,030 Suppose now you create apps in your local machine so your kid doesn't know about your apps. 782 00:57:08,030 --> 00:57:12,100 So you have to link your local apps with the good stuff, right? 783 00:57:14,150 --> 00:57:21,050 Yeah, yeah, this is assuming this is assuming that I assume you and I are on the same team and I created 784 00:57:21,050 --> 00:57:23,330 an app and posted, you pulled it. 785 00:57:24,050 --> 00:57:30,140 So if you do this or the only instance knows we are to get you in, we have to get to where you go up 786 00:57:30,140 --> 00:57:32,680 from so it again, it can do it OK. 787 00:57:33,290 --> 00:57:35,020 Are you using VentureBeat? 788 00:57:36,920 --> 00:57:43,090 Yes, this is what I'm using it, it's just the update of all all the apps of my Bentley. 789 00:57:46,220 --> 00:57:49,970 Yeah, I think I will explore that. 790 00:57:49,970 --> 00:57:50,690 Thank you so much. 791 00:57:51,110 --> 00:57:55,070 You don't do bench pool, Paul sports. 792 00:57:55,070 --> 00:57:57,230 Nothing good will get pushed. 793 00:57:57,830 --> 00:57:58,180 No. 794 00:57:58,550 --> 00:58:02,030 This bench update that you can issue to the. 795 00:58:02,030 --> 00:58:06,290 Come on, Karen, you will see all the steps that is doing. 796 00:58:07,410 --> 00:58:16,500 And you see some progress while it's doing the update, if you if you want to push good from your local 797 00:58:16,500 --> 00:58:18,820 machine to the gate folders. 798 00:58:19,560 --> 00:58:28,200 Are you using this update again or you have the update is only to bring the the change from the remote, 799 00:58:28,710 --> 00:58:36,140 uh, remote GitHub and then running benchmark rate and running patch and doing all the stuff. 800 00:58:36,990 --> 00:58:38,920 I think it's doing a lot of stuff. 801 00:58:39,070 --> 00:58:40,680 I don't know everything, but. 802 00:58:42,360 --> 00:58:49,170 OK, this is the comment we see in the tutorial, in the documentation, so I just wanted to be sure 803 00:58:49,170 --> 00:58:50,060 it was doing this. 804 00:58:50,820 --> 00:58:58,920 But it is this is I feel it is not you cannot control the game because if you are in production and 805 00:58:58,920 --> 00:59:08,820 you issue a bench update, even your IRP next up will get updated and your therapy up app get updated. 806 00:59:09,180 --> 00:59:11,460 And you don't want this update. 807 00:59:11,490 --> 00:59:12,690 Yes, yes, yes. 808 00:59:12,690 --> 00:59:13,020 Yeah. 809 00:59:13,030 --> 00:59:15,520 You raise money that will actually happen. 810 00:59:15,780 --> 00:59:19,070 Yes, yeah, yeah. 811 00:59:19,180 --> 00:59:21,820 You want to test, for example, if you are in the least. 812 00:59:21,840 --> 00:59:24,190 Well, and now there is 13. 813 00:59:24,390 --> 00:59:25,530 It's very dangerous. 814 00:59:26,370 --> 00:59:29,280 So we have to pick which update you want. 815 00:59:32,650 --> 00:59:42,640 OK, and another question about the pull request with contribution with the AARP, next. 816 00:59:42,880 --> 00:59:48,730 So if you have and you want to contribute back to AARP next, how to do this? 817 00:59:52,780 --> 00:59:53,260 Will come 818 00:59:56,200 --> 00:59:56,520 here. 819 00:59:56,720 --> 01:00:00,970 Yeah, I will come back to you just this question come back to you. 820 01:00:01,340 --> 01:00:01,690 Yes. 821 01:00:02,110 --> 01:00:13,360 Now you have created a new features, awesome, awesome features, which probably will they will be 822 01:00:13,420 --> 01:00:18,920 happy and they will pay you to get merged in their application. 823 01:00:18,940 --> 01:00:20,620 So how to contribute back? 824 01:00:22,540 --> 01:00:22,910 Yeah. 825 01:00:22,930 --> 01:00:25,720 Remember remember Europeanist, this opensource. 826 01:00:25,730 --> 01:00:32,890 So what you need to do is to check out your brand and then you push, you push whatever you have done 827 01:00:32,890 --> 01:00:34,600 on your branch to the repository. 828 01:00:35,050 --> 01:00:37,750 And then what they normally do is that we have to review that. 829 01:00:37,970 --> 01:00:43,780 So before before they take it and get it onto the application, they will have to it has to go through 830 01:00:43,780 --> 01:00:44,650 rigorous testing. 831 01:00:44,650 --> 01:00:49,170 And so what they have to do and get in, get show us and get what to do. 832 01:00:50,330 --> 01:00:50,650 Great. 833 01:00:51,220 --> 01:00:54,850 No, that one is I would say this could be its GitHub stuff. 834 01:00:55,240 --> 01:00:57,750 So check out your your custom brands. 835 01:00:59,560 --> 01:01:04,490 It's a it's a tough topic to get out of it, OK? 836 01:01:04,900 --> 01:01:08,910 It's a great we are talking about get only if GitHub topic. 837 01:01:08,920 --> 01:01:09,220 Yeah. 838 01:01:09,580 --> 01:01:10,120 Yeah. 839 01:01:14,400 --> 01:01:24,360 I don't think it's very difficult, but under under your get the repository you have or you never do 840 01:01:24,360 --> 01:01:24,590 it. 841 01:01:24,770 --> 01:01:28,290 I, I feel that has never contributed. 842 01:01:28,300 --> 01:01:30,460 But we are fenigstein. 843 01:01:31,680 --> 01:01:34,000 Well, I have not done it yet. 844 01:01:34,080 --> 01:01:35,730 I still have plans to do it. 845 01:01:36,540 --> 01:01:42,390 But it is it is as easy as just taking out your custom branch and then proceed to the repository. 846 01:01:43,020 --> 01:01:43,560 That's it. 847 01:01:43,620 --> 01:01:47,870 Then the next steps will be the first two steps. 848 01:01:47,880 --> 01:01:52,960 But I want to see it and get out to the front end. 849 01:01:53,480 --> 01:01:55,220 I can I can do it. 850 01:01:55,230 --> 01:01:55,920 I can show you. 851 01:01:55,920 --> 01:01:56,280 I can. 852 01:01:56,280 --> 01:01:58,050 Do you are we doing it with you. 853 01:01:58,450 --> 01:02:00,240 OK, but I've got to get up. 854 01:02:00,600 --> 01:02:01,010 Get up. 855 01:02:01,040 --> 01:02:05,160 If you check out to create a branch you should use the command. 856 01:02:05,550 --> 01:02:05,840 No. 857 01:02:06,180 --> 01:02:06,900 Yes sir. 858 01:02:07,000 --> 01:02:07,800 I have a question. 859 01:02:11,120 --> 01:02:17,420 For our case, I'm going to work with the mom and dad in the same project. 860 01:02:17,920 --> 01:02:22,540 OK, so how can we handle that? 861 01:02:28,510 --> 01:02:30,950 Look, we do care that we took care of that, right? 862 01:02:33,260 --> 01:02:40,250 Sorry, sorry, Karenni money, we took care of that in the earlier today. 863 01:02:40,880 --> 01:02:43,960 Yeah, I will give him any Uzma. 864 01:02:43,970 --> 01:02:46,130 It's better to review the decision. 865 01:02:46,610 --> 01:02:55,700 Uh, and if you have a question or doubts, come back tomorrow or we'll discuss or we will clarify it 866 01:02:55,700 --> 01:02:56,150 again. 867 01:02:56,690 --> 01:03:01,400 So it's very well discussed or. 868 01:03:02,190 --> 01:03:09,050 OK, so, uh, today we completed this, uh, topic, I think. 869 01:03:10,020 --> 01:03:16,170 And it's still open and you get if you are working during this training and you have a question for 870 01:03:16,280 --> 01:03:16,510 it. 871 01:03:16,710 --> 01:03:20,370 We are open to accept questions related to it. 872 01:03:20,880 --> 01:03:24,290 And it's a large topic. 873 01:03:24,540 --> 01:03:25,620 It's very, very large. 874 01:03:26,400 --> 01:03:34,680 But we took a small part of it, which is very important to cooperate with the other team members. 875 01:03:36,240 --> 01:03:38,610 OK, very good. 876 01:03:38,880 --> 01:03:39,600 Very good. 877 01:03:40,200 --> 01:03:41,220 That's it for today. 878 01:03:41,640 --> 01:03:45,300 So let's see you tomorrow, inshallah. 879 01:03:45,700 --> 01:03:48,840 For the same time for another topic. 880 01:03:52,250 --> 01:03:58,430 Thank you, thank you, thank you, thank you, thank you, Karen. 881 01:04:02,020 --> 01:04:04,190 Good bye, my.